This repository has been archived by the owner on Mar 4, 2024. It is now read-only.
EVEREST-832 Fix access to namespaces #444
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oksana-grishchenko
approved these changes
Feb 12, 2024
Co-authored-by: Oksana Grishchenko <[email protected]>
Co-authored-by: Oksana Grishchenko <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix access to namespaces
Problem:
EVEREST-832
DBCs and DBBs had access to all BackupStorages and MonitoringConfigs regardless of the namespace.
Cause:
We weren't validating if a given BackupStorage or MonitoringConfig was allowed in the DBC's namespace.
Solution:
Validate if a given BackupStorage or MonitoringConfig is allowed in the DBC's namespace.
CHECKLIST
Jira
Tests